Save card details/Card Vault (FSP-2126) is an update to the standard payments page checkout facility allowing merchant's to pass their merchant Id and customer Id and have their clients previously saved card automatically display as payment options on UCF.
If the "Allow Save Customer Card Details" function is enabled on the merchant's configuration in TransSmart
(see Figure 1. Allow Save Customer Card Details) and a unique merchantidentifier and customeridentifier is passed in a form post to the payment page, the ability to save a card will be available.
On a customer's first transaction they will be shown the normal payment page with a check-box to save the card they are currently using.
This is available on all card transactions ie: Visa, MasterCard, Amex and Diners).
If the check-box is selected the customers card will be stored in the Card Vault. The card PAN (number) and expiry-date will be encrypted and stored.
When a customer navigates to the payment page again on a subsequent transaction, a new payment type on the left menu will appear called "Saved Cards".
The customers saved cards are listed here, a maximum of 5 saved cards are allowed per customer.
A customer will then be able to make use of a saved card by entering only the required "Security Code" (CVV) for the chosen card.
If a Supplier is setup to belong to a particular Supplier Group (see Figure 1. Allow Save Customer Card Details)
then this will allow all merchants defined for that Supplier Group to present the customers saved cards on the payment checkout page.
A consistent and unique customer identifier must however be applied across all merchants customers within that Supplier Group
(i.e. different sub-merchants within that organisation/Supplier Group should not have their own customer identifiers, otherwise they are treated as distinct entities)
Any card that was then saved by that customer for other merchants belonging to the same Supplier Group will be available.
(This for instance will facilitate various merchants across the Vodacom Group to leverage customers saved cards across different purchase journeys for different products)
Figure 1. Allow Save Customer Card Details
1.2 In-Scope
The following items are in-scope for this release:
Save Card Details
Merchant Config Setting
Card Vault API
Merchant Interface Payments
1.3 Payment Types
The Vodacom Payment Gateway will accept the following payment types as allowable payment options, which must be configured per merchant:
Mastercard
Visa
1.4 Role-players in the system
1.4.1. Payment Broker
Secure website hosted in Vodacom secure domain that allows merchants to broker or facilitate a call to the Payment Gateway payment checkout page via secure URL.
The Broker will construct a URL that will act as though the merchant is integrating directly with the payment gateway.
1.4.2. Payment Gateway
Secure website hosted in Vodacom secure domain that allows customer to pay for the goods purchased from merchant.
1.4.3. Customer
Defined as a person requesting the payment for goods.
1.4.4. Merchant
Defined as a business or person that provides the goods to the customer, and the merchant will integrate to the VPG.
The merchant must meet the conditions listed in the following table.
Table 2. Merchant Prerequisites
#
Condition Type
Condition Details
1.
Bank Registration
The merchant must have a valid merchant registration for eCommerce transactions with Nedbank (Vodacom Financial Services Acquiring Bank)
2.
Hosted Pages
Hosted pages belong to the Payment Gateway in this instance.
Branding can be applied to the merchant templates for the payment checkout page, and the outcome of the customer payment.
For more detail refer to Section 6: Merchant Templates of the Merchant Interface Payments Page v2.1 specification
3.
Merchant Configuration
Vodacom Payment Solutions Operations team must configure merchant details on TransSmart.
The following information is required:
